System and method for providing customizable options on a wireless device

ABSTRACT

A system and method for enabling users to send and receive messages and other information from mobile devices and enabling users to access server-based information using mobile devices over wireless data networks are disclosed. The present invention enables users to customize information that is received and sent from mobile devices. For example, the user may select to receive emails (or other correspondences) from a particular individual or group of individuals. The user may also select to receive a particular type of types of emails (or other correspondences), such as the ones marked as high priority or otherwise designated as being important. Other variations may also be implemented. In addition, the user may customize responses, replies and other outgoing information from the user&#39;s mobile device. Mobile device users may also customize various aspects of views and applications. Examples of customizable options may include home page (e.g., personal, any URL), time zone, date format, font format, language and other options.

FIELD OF INVENTION

[0001] The present invention relates generally to the field of wirelessdevice access and, in particular, to a system and method for enablingusers to customize views and options for messages and other informationreceived and displayed on mobile devices and enabling users to accessserver-based information using mobile devices over wireless datanetworks.

BACKGROUND OF THE INVENTION

[0002] Generally, mobile devices provide various communicationcapabilities to users. Currently, users may access the Internet throughpersonal mobile devices. For example, users may read local and worldnews headlines and/or short summaries on a mobile device, such as a PDA,cell phone, pager, etc. Users may also receive alerts and predeterminedtriggers, such as stock movement and other events. However, the amountand type of information received may be limited due to hardware andphysical limitations of a mobile device. For example, informationreceived on a mobile device may not be easily viewable due to thelimited screen space of a mobile device.

[0003] While mobile devices may access information through the Internet,access to a corporate or other network may be limited. Also, informationtransferred from a server on a network to a mobile device may requireconversion to a form viewable on a mobile device. This process mayrequire restructuring and re-writing applications and othermodifications. Oftentimes, users may need to access critical data andother information stored on the user's personal computer located on acorporate (or other) network. However, such information may not beeasily accessed through a mobile device due to conversion and displaylimitations. Thus, information retrieval may be limited to mobile users.

[0004] Mobile devices and wireless networks rely on a broad spectrum oftechnology. In comparison to personal or desktop computers, each classof mobile device may currently represent a unique hardware and softwareplatform. For example, mobile phones and PDAs may have varyingcapabilities and limitations as computing devices and client devicesaccessing corporate and other networks. The wireless networks thatsupport mobile devices may be similarly diverse.

[0005] In addition, users may find viewing, storing, sending, andmaneuvering through information displayed on a mobile device to bedifficult and limiting. This may be due to the lack of customizationavailable on mobile devices.

[0006] These and other drawbacks exist with current systems.

SUMMARY OF THE INVENTION

[0007] Additional advantages of the invention will be set forth in partin the description which follows, and in part will be obvious from thedescription, or may be learned by practice of the invention. Theadvantages of the invention may be realized and attained by means of theinstrumentalities and combinations particularly pointed out in theappended claims.

[0008] The present invention provides interactive access to variousdatabases and directories from web-enabled mobile devices, such ascellular phones, pagers, and PDAs. The present invention enables users(e.g., users of Lotus Notes™) to remotely interact with messaginginfrastructure using a variety of mobile devices over wireless datanetworks. The present invention offers broad sets of features thatextend the reach of services to small, wireless devices, such ascellular phones, pagers, PDAs with wireless modems. Users may send andreceive messages, alerts, pages, notifications and other forms ofinformation to mobile devices from the user's desktop. Wireless accessfeatures of the present invention enable users to remotely accessservers over wireless data networks and interact with databases andpublic directories using mobile devices equipped with micro-browsers.

[0009] The present invention enables users to customize information thatis received and sent from mobile devices. For example, the user mayselect to receive emails (or other correspondences) from a particularindividual or group of individuals. The user may also select to receivea particular type of types of emails (or other correspondences), such asthe ones marked as high priority or otherwise designated as beingimportant. Other variations may also be implemented. In addition, theuser may customize responses, replies and other outgoing informationfrom the user's mobile device. For example, a user may select from alist of possible customized replies.

[0010] Mobile device users may customize various aspects of views andapplications. Examples of customizable options may include home page(e.g., personal, any URL), time zone, date format, font format, languageand other options.

[0011] The accompanying drawings, which are incorporated in andconstitute a part of this specification, illustrate various embodimentsof the invention and, together with the description, serve to explainthe principles of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012]FIG. 1 is a diagram of a functional overview of an overall system,according to an embodiment of the present invention.

[0013]FIG. 2 is a diagram of a wireless servlet, according to anembodiment of the present invention.

[0014]FIG. 3 is a diagram of a mobile application development tool,according to an embodiment of the present invention.

[0015]FIG. 4 is a diagram of modules for a mobile device access system,according to an embodiment of the present invention.

[0016]FIG. 5 is a diagram of functions available on an electronic mailmodule, according to an embodiment of the present invention.

[0017]FIG. 6 is an example of a screen shot of a mail menu for a mobiledevice, according to an embodiment of the present invention.

[0018]FIG. 7 is an example of a screen shot of an action menu for amobile device, according to an embodiment of the present invention.

[0019]FIG. 8 is an example of a screen shot for a new memo for a mobiledevice, according to an embodiment of the present invention.

[0020]FIG. 9 is a diagram of functions available on a calendar module,according to an embodiment of the present invention.

[0021]FIG. 10 is a flowchart of a process for formatting a document inan appropriate format for a device, according to an embodiment of thepresent invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] Mobile services of the present invention enable desktop and webbrowsers (e.g., users of Lotus Notes™) to communicate directly with one-and two-way wireless devices worldwide. The present invention allows foreasy administration for multiple wireless services, while giving eachuser the ability to control when and what may be received on the user'smobile devices. Users may get direct access to electronic mail,calendar, public directories and other information from theirdata-capable cell phone, interactive pager or other wireless device, viaa wireless service provider. Wireless device access enables users tohave instant access to critical information wherever the user may happento be, via a wide range of communication devices and wireless networks.

[0023] Users may also customize the information that is received andsent from mobile devices. For example, the user may select to receiveemails (or other correspondences) from a particular individual or groupof individuals. The user may also select to receive a particular type oftypes of emails (or other correspondences), such as the ones marked ashigh priority or otherwise designated as being important. Othervariations may also be implemented. In addition, the user may customizeresponses, replies and other outgoing information from the user's mobiledevice. For example, a user may select from a list of possiblecustomized replies, which may include “will discuss later”, “will calllater” and other replies. Customized replies may be predetermined forvarying types of actions. For example, for a stock broker, possiblereplies may include “buy”, “sell”, “hold”, etc.

[0024] Various messaging services may be available through the presentinvention. For example, mobile services may convert mail messages inorder to transmit the mail messages to mobile devices over a variety ofdata messaging networks including paging services, cellular phonenetworks, wireless data networks, and other networks. Users may composemail messages using a mail template (or form) and address them to mobiledevice recipients using an email alias (e.g., “John Smith Mobile”).Users may compose messages with standard mail memo and address messagesto e-mail and mobile device recipients. Email messages may be routednormally and messages intended for pagers or other wireless devices maybe routed through a foreign domain.

[0025] The outbound message may be converted into an appropriate formatfor the device and data network and may be forwarded via modem or IPconnection to the service provider. The wireless service may thentransmit the message to the appropriate mobile device. According to anembodiment of the present invention, a sender of the message may addacceptable replies at the end of an outgoing message to receive animmediate answer from the mobile device user. These replies may be sentto the mobile device along with the message. Mobile services may thenpoll the wireless service provider periodically looking for the responsefrom the message recipient. Once received, the response may be depositedin the originator's mail inbox.

[0026] A wireless access server of the present invention allows mobileusers to use a variety of devices to access information in servers viawireless IP service providers. A wireless access server may act as aproxy for handling communications between the server and mobile devices,such as cellular phones, PDAs, two-way pagers equipped with text-basedmicro-browsers and other devices. Text-based browsers may use handhelddevice markup language (“HDML”) to send requests and receive data viawireless IP data network to HDML servers which reside at the wirelessservice provider's operations center. The HDML server may forward therequests to the MSD server via frame relay or SSL Internet connection. Awireless access server may interpret the request, act as a proxy betweenthe mobile device and the server, and pull the requested informationfrom one or more databases. The information may be formatted by thewireless access server and sent back to the mobile device.

[0027] An end user may use a wireless device to navigate a series ofmenus to request information from the server. The wireless access servermay allow access to an end user's mail account, calendar, publicdirectory and other information.

[0028] For example, an end user may view a personal mail inbox or searchfor messages by date, sender, subject or other criteria. The user mayread mail messages, forward messages to other recipients or fax hardcopies of the messages to one or more fax machines. Other operations mayalso be performed. The user may also compose a new mail memo, deleteunwanted messages from the mail database and save drafts of memos andother information.

[0029] An end user may also perform various scheduling operations. Forexample, the user may view daily schedules and send selected one or moreschedules to one or more fax machines or other recipients. Thus, if amobile user's administrative assistant or colleague creates a newappointment or edits an existing appointment, the user may be notifiedof the changes immediately. Users may also create new calendar entries,including appointments, events, reminders and other entries.

[0030] A public directory may also be accessible to a user through awireless device, such as a cell phone, PDA, pager or other device. Otherdirectories maintained through the server may also be accessed. Forexample, a personal or private directory created by the user andmaintained on the server may be accessed. A user may search the public(or other) directory by last or first name (or other criteria) and viewthe individual person records on the mobile device. Once the appropriateperson is located and displayed, the user may automatically create anemail message or initiate an outgoing call.

[0031] According to another embodiment of the present invention, userswho are external to an entity's messaging infrastructure may access themobile services of the present invention. An entity may include abusiness, corporation or other group of individuals. A web site may becreated which enables users from outside the entity to compose messagesand receive responses from mobile device users. A customer or businesspartner may point their browser to the web site, compose a message, andselect one or more recipients from a list of mobile device users in theentity, e.g., corporation. The list of registered device users may becontrolled (or maintained) by a system administrator or other authorizedentity. For example, individuals that may be accessible by customers,prospects and partners may be listed on the web site.

[0032] Mobile services may provide a set of enhanced applicationinterface extensions, enabling developers (or other authorized entities)to configure custom mobile applications for use on handheld, wirelessand mobile devices. For example, to enhance an organization'sresponsiveness to customers, users may enable an existing customer caresolution to distribute messages (or other information) to a remotecustomer service representative via pager, cell phone or other mobiledevice, upon receipt of a predetermined trigger, such as a troubleticket or other alert. The representative may then send a reply to thecustomer's email address instantly from the mobile device.

[0033] The present invention further enables IT managers, systemsadministrators and other authorized entities with enhanced securityfeatures that may include the ability to restrict the devices andwireless services that are allowed to access information and/or data.

[0034] Incompatibility issues may exist when enabling email functionsand access to information from various databases on a server via amobile device. For example, mobile devices may not have certaincapabilities and viewing options available on a desktop computerconnected to a network. Physical and technological impediments mayexist. For example, the screen of a mobile device, such as cell phone,may not be able to support a large amount of text due to the cellphone's compact size thereby limiting the amount of information viewableat once. Also, certain texts, images and other attachments may not beeasily viewable or accessed by a mobile device, due to limiting screensize and other capabilities. Also, as mobile devices may be used toaccess information from anywhere in the world, various time/dateincompatibilities may exist as well.

[0035] The present invention may create and customize style sheets thatmay be applied to data sent to and from a mobile device. The presentinvention provides a method and system for converting data sent to andfrom a mobile device in a format that may be understandable to a mobiledevice and viewable on a mobile device.

[0036]FIG. 1 illustrates a diagram of a functional overview of anoverall system for providing wireless device access, according to anembodiment of the present invention. One or more clients 110 may accessa server 120 through a desktop terminal. In addition, one or more remoteweb clients 112 may access server 120 through Internet 114 or othercommunication means. Server 120 may comprise various modules, databasesand other functions, such as tool 122 and servlet 124. In addition, oneor more databases 128 ₁-128 _(N) may store information related toelectronic mail, directories, calendar, scheduling applications, and/orother applications. Other components, functions and databases may alsobe provided. A wireless access server 126 may be connected to a MobileServer Provider 116, which may also communicate through Internet 114.Mobile Server Provider 116 provides communication with one or moremobile devices 130, such as a pager, a cell phone, a PDA and otherwireless devices. This system enables a wireless device to access andinteract with information stored and maintained on Server 120. Thepresent invention further provides that the information transmitted toand from mobile device 130 will be in a format acceptable for displayand access on a mobile device.

[0037] The wireless implementation of the present invention may includea mobile application development tool 122 and a wireless servlet 124which runs on Server 120. Other components, tools and applications mayalso run on Server 120. Tool 122 may serve to allow the design of amobile version of applications to run (or execute) successfully onvarious wireless devices. Servlet 124 may provide wireless device usersreal-time access to various databases and other information maintainedon Server 120. Thus, the present invention provides an infrastructurethat allows devices using other markup languages to be supported usingthe same or similar architecture.

[0038]FIG. 2 illustrates a diagram of various subsystems of a wirelessservlet, according to an embodiment of the present invention. WirelessServlet 124 may include various subsystems, such as servlet subsystem210, request dispatcher 212, request handlers 214 ₁- 214 _(X), userapplication preferences 216, page generator 218, application designmanager 220, XSLT processor 222, XML parser 224, XML-notes translator226, log 228, and administrator 230. Other subsystems, modules,functions and components may also be implemented.

[0039] Servlet subsystem 210 may be a class derived from a HTTP servletbase class that receives Get, Post and other requests from a device,such as a mobile device via a Wireless Application Protocol (“WAP”)server 240, for example, for providing applications over wirelesscommunication networks, through HTTP 242, TCP/IP 244 or otherconnection. It may be written in Java or other programming language.Servlet subsystem 210 may interface with request dispatcher 212. Serversubsystem 210 may use JNI (or other mechanism) to pass requestdispatcher 212 each request with user data, HTTP header information,session identifier and other information. In return, request dispatcher212 may return a response along with session information and otherinformation. Request dispatcher 212 may be responsible for retrievingthe correction session context, invoking the correct request handler 214₁-214 _(X) for each request, and returning one or more responses toservlet subsystem 210. Request handlers 214 may process one or morerequests from the device and send response pages back to the device,such as WML decks or WML script bytecodes. For example, request handlers214 may exist for requests, such as login, open application, and sendmail. Request handlers 214 may also update the session state and otherinformation. Request handlers 214 may include requests related to basicoperations (e.g., open application, read, view, open document, readitem, edit document, save document, delete document, create document,etc.), electronic mail (e.g., compose mail, send mail, save draft,etc.), calendar (e.g., process invite, read calendar, add calendar,schedule meeting, fax calendar, etc.), search functions (e.g., addresssearch, find address, application search, etc.), and miscellaneous(e.g., edit user profile, save user profile, login, go to home deck,load script, move to folder, session term, etc.).

[0040] User application preferences 216 may manage user-specificsettings for a particular application. The designer of a mobileapplication may include application specific mobile settings, such asuser preferences, as part of the application design. Applicationspecific settings may also include settings such as the default form orview to use. Page generator 218 may be responsible for creating contentpages, such as WML decks, which may be sent to a wireless device. It mayuse XML-Notes translator 226 to convert data to XML, the applicationdesign manager 220 to retrieve XSL style sheets and XSLT processor 222to produce the output page.

[0041] Application design manager 220 may be responsible for retrievingmobile application design information, such as XSL style sheets used forcombining document data with forms.

[0042] Application design manager 220 may also retrieve design elementsfrom an application (or other) database. XSLT processor 222 maytransform an XML document to a different XML document based on an XSLstyle sheet. For example, a document represented in a markup languagemay be transformed to a representation in WML using XSLT processor 222.XML Parser 224 may provide the capability to parse XML documents usingDOM, SAX or other objects. XML-Notes translator 226 may be used totransform documents and view data from an internal format to XMLdocuments. Log 228 may track and maintain errors and other events.Administrator 230 may provide administration and configurationinformation, which may be stored in one or more databases, to othersubsystems. Wireless-specific user settings may include the user'swireless homepage and locale settings, such as the language used by theuser.

[0043]FIG. 3 illustrates a diagram of various subsystems of a mobileapplication development tool, according to an embodiment of the presentinvention. A mobile application development tool may include varioussubsystems, such as user interface 310, compile manager 312, designfilter 314, script compiler 316, style sheet generator 318, outputpackager 320, log 322, XSLT processor 324, XML parser 326, and Notes—XMLtranslator 328. Other subsystems, modules, functions and components mayalso be implemented.

[0044] User interface 310 may include a form which may be completed byan application designer (or other authorized entity) in order toidentify the design elements that may be used in a mobile application.User interface 310 may pass a compile document to compile manager 312 inorder to produce a compiled mobile application. Compile manager 312 mayreceive one or more compile requests from user interface 310 where oneor more other subsystems may complete the compilation process.

[0045] Design filter 314 may validate that the design elements do notcontain elements that are not needed or are not supported by thedestination device (e.g., mobile device). Elements not needed may beremoved and elements that are not supported may result in compile and/orother errors. Script compiler 316 may convert a subset of @functions andJavaScript (or other script) to WML script (or other wireless script).Other scripts may also be converted to WML script. Style sheet generator318 may use XSL style sheets to generate application specific XSL stylesheets that may become part of a compiled mobile application and may beused by a wireless servlet at run-time. Other types of style sheets mayalso be generated. Output packager 320 may store a compile output in aspecial mobile class. Compile output may include an application digest,style sheets and script compilation units. Other information may also beincluded in a compile output. Log 322 may track and/or record errors andother events.

[0046] XSLT processor 324 may transform an XML document representing adesign element, such as a form, to an XSL style sheet based on anotherXSL style sheet. XML parser 326 may provide the capability to parse XML(or other) documents using DOM, SAX or other objects. Notes—XMLTranslator 328 may transform design elements from an internal format toXML documents or other form of documents.

[0047] Style sheets may be both input and output of a mobile applicationcompilation process. Style sheets may include view, read document, editdocument, create document, forward document, read item, read mail, editmail, create mail, read invitation, read calendar, edit calendar, createcalendar, search address, search application, user profile and others.

[0048]FIG. 4 is a diagram 400 of modules available on a mobile deviceaccess system, according to an embodiment of the present invention.Various modules and functions may be available through the system of thepresent invention. Modules may include email module 410, calendar module412, forms module 414, view/folders module 416, default and customactions module 418, customization module 420 and search module 422.Other modules may also be implemented.

[0049] The present invention allows WAP browser enabled wireless devicesaccess to various applications. Users may access email, calendar,personal, public and other directories from mobile devices, such ascellular phone, interactive pager, PDA, via a wireless service provider.

[0050] As various applications may be supported, a user may customizethe type of information, the format of the information and othercharacteristics related to information received on a mobile device. Forexample, a user may customize various rules or priority instructions forviewing received information on a mobile device. A user may request arule where email (or other information and correspondences) receivedfrom a particular person or group of persons may be sent to anidentified mobile device. Alerts may also be programmed for a particularperson or group of persons or other predetermined triggering events(e.g., stock activity). The user may also limit messages (or othercorrespondences) sent to an identified mobile device to messages markedwith high (or other level of) priority or otherwise identified as beingimportant. Viewing options may include enabling the user to choose whichfeatures (or lines) of a message that the user would like to makeviewable. For example, the user may want to limit incoming message viewsto select fields, such as From field and subject line field, which mayinclude up to a predetermined number of characters. Other customizedrules and viewing options may be defined by the user and applied by thesystem of the present invention. Other customizations and options may beavailable.

[0051]FIG. 5 illustrates various functions and operations may beavailable through an email module, according to an embodiment of thepresent invention. Email module 410 may include mail menu 510, actionmenu 512, address book 514, draft lists 516, trash lists 518, new memo520 and search 522. Other functions and operations may also beavailable.

[0052]FIG. 6 illustrates an example of a mail menu as displayed on amobile device, according to an embodiment of the present invention. Themail menu screen 600 may include various viewing options which the usermay select. Viewing options may include viewing new mail by date 610,new mail by author 612, inbox by date 614, inbox by author 616, drafts618, trash 620, and all documents 622. Other viewing options may alsoinclude new memo 624, search all 626 and other views.

[0053] New mail may be displayed to the user where the user may specifya criteria for a display list, such as new mail by date, by author, bysubject and other criteria. For example, new mail by date 610 maydisplay a list of unread messages from an inbox folder to the user,received on a particular date or range of dates. Information associatedwith each message may be displayed to the user, such as the subject ofeach message. A user may also select to view the first predeterminednumber of words or letters of the message and/or subject for a quickview. A viewing order may be implemented to display the messages, suchas chronological, reverse chronological, alphabetical and other viewingorders. New mail by author 612 may display a list of messages accordingto a specified sender (or originator). New mail by author 612 may alsodisplay messages according to a string entered, such as part of anidentifier (e.g., name) associated with one or more senders. The stringmay include characters of the last name, first name, or other identifierof one or more senders.

[0054] Inbox by date 614 may display a list of messages to the userwhere all messages from an inbox folder may be included. Informationassociated with each message may be displayed, such as subject, author,etc. Reverse chronological or other identified order may be used todisplay the messages. Inbox by author 616 may display messages by anidentified author or authors with a common string of characters or othercriteria.

[0055] Drafts view 618 may display a list of messages to the user wheresome or all messages from a drafts folder may be included. Informationassociated with each message may be displayed, such as subject, author,etc. Trash view 620 may display a list of messages from a trash folder.Information associated with each message may be displayed, such assubject, author, etc. All documents view 622 may display all currentdocuments available to the user. Various display orders may be used,such as chronological, reverse chronological, alphabetical, etc.

[0056] New memo view 624 may allow the user to create and send a newoutgoing mail message. Search all view 626 allows the user to search themail database for all messages which match a criteria.

[0057] Phone keys 640 may serve as short cut keys for moving to theoption with the corresponding number, thus selecting the option andinvoking it. Arrow 630 indicates to the user which option may becurrently invoked.

[0058]FIG. 7 illustrates an example of an action menu for a mailapplication as displayed on a mobile device, according to an embodimentof the present invention. The action menu screen 700 may include variousaction options which the user may select. Action options may includemultilist 710, reply 712, delete 714, fax 716, forward 718, search 720,mail menu 722. Other action options may also be implemented.

[0059] Multilist 710 enables the user to view multiple selected messagesat once. For example, the contents (or selected information) of two ormore messages may be displayed in a single view. Reply 712 enables theuser to reply to a selected message. Various reply options may also beavailable. For example, a user may select to reply, reply with history,reply to all, and reply to all with history. User defined customizedreplies may also be available. Other reply options may be available.Delete 714 enables the user to delete a selected message where thedeleted message may be moved to a trash folder. In addition, a deletemessage may be displayed to the user to confirm this action. Fax 716 maysend the selected message to one or more fax machines specified by theuser. Forward 718 enables the user to forward a selected message in anew memo. Search 720 enables the user to search the current view formessages which match the supplied criteria. A search string entered bythe user is matched if the field contents contain the entered searchstring. Mail menu 722 navigates the user back to the mail applicationmenu. Other options may be available to the user, such as access to acalendar application, address book application and other applications.

[0060] Phone keys 740 may serve as short cut keys for moving to theoption with the corresponding number, thus selecting the option andinvoking it. Arrow 730 indicates to the user which option may becurrently invoked.

[0061] Address book functionality, as shown by 514 in FIG. 5, mayprovide the user with a list of recipients for an email or othercorrespondence, according to an embodiment of the present invention. Theaddress book may display information of individuals stored in a public,private, personal and other directories. Information may include a listof individuals, including full name, email address, various phonenumbers, address information, aliases and other personal and contactinformation.

[0062] Draft lists may be displayed, as shown by 516 in FIG. 5, to theuser, according to an embodiment of the present invention. Draft listsmay be displayed as a list of draft view messages where messages may bedisplayed in descending date order. Other viewing orders may also beimplemented. Drafts may include messages or other memos that have notbeen completed or sent yet.

[0063] Trash lists may be displayed, as shown by 518 in FIG. 5, to theuser, according to an embodiment of the present invention. Trash listmay display a list of messages in a trash folder, according to aparticular order, which may include descending order by date, ascendingorder by date, or other specified order. Emails or other messages thathave been deleted may be stored in a trash folder.

[0064] New memo functionality, as shown by 520 in FIG. 5, may beavailable, according to an embodiment of the present invention. FIG. 8illustrates an example of a screen for composing a new memo, asdisplayed on a mobile device, according to an embodiment of the presentinvention. A new memo may include various fields. For example, arecipient field may be identified in line 810. One or more recipientsmay be identified as well as groups of recipients. An information copyof the memo may be sent to an identified recipient in line 812. Line 814may enable the user to send one or more recipients a blind informationcopy of the memo where other recipients may not see the one or morenames (or other identifier) specified in line 814. Subject field 816enables the user to enter text for the subject of the outgoing mailmessage. Body field 818 may contain the text for the body of theoutgoing mail message. Memo options may include sending the message,canceling the message, saving the message as a draft and other options.Other fields and operations may be implemented. According to anembodiment of the present invention, each field (e.g., 810, 812, 814,816 and/or 818) may be a separate screen on a mobile device.

[0065] Search functions, as shown by 522 in FIG. 5, may also beavailable to the user, according to an embodiment of the presentinvention. Search criteria may include searching messages (e.g., emails,memos, and/or other correspondences and documents) based on variousfields, such as sender, date, subject and other parts of a message.Other search criteria may also be used. For example, a user may selectthe sender (or from) field to enter text (e.g., a character, string ofcharacters, etc.) which may be used to match the sender (or from) fieldin documents in a mail or other database. The search may use a“contains” mechanism which may give a positive match on any documentwhich has a sender (or from) field containing the text string provided.A user may also select a subject field to enter text which may be usedto match the subject field in documents in a mail or other database. Thesearch may use a “contains” mechanism which may give a positive match onany document which has a subject field containing the text stringprovided. In addition, the user may select a date field to enter a datewhich may be used to match the delivered (or sent) date in documents ina mail or other database. The search may use a “since” mechanism whichmay give a positive match on any document which has a delivered (orsent) date greater than or equal to the data provided. Other searchmechanisms may also be implemented. Other fields may also be used tosearch from. Numeric strings and/or text and number combination stringsmay also be used as search criteria.

[0066]FIG. 9 illustrates various functions and operations that may beavailable through a calendar module, according to an embodiment of thepresent invention. A calendar module 412 may provide a menu of options.For example, view 910 may provide viewing options, such as daily view,weekly view, monthly view and other selected time frames. Also, addappointment 912 may enable a user to add one or more appointments,delete appointment 914 may enable a user to delete one or moreappointments and modify appointment 916 may enable a user to modify oneor more existing appointments. Other operations are also available. Auser may schedule one or more meetings with various participants throughschedule meeting 918. Intended participants may include individualsstored in databases, directories and/or address books. One or morecalendar entries and other various information may be forwarded/sent toone or more recipients through send 920. For example, selected calendarentries may be faxed or emailed to recipients. Other operations may alsobe available.

[0067] Various functions and operations may be available through a Formsmodule 414, according to an embodiment of the present invention. Thepresent invention may create forms that the end user may use to display,edit or create new documents on a wireless device. Also, these forms mayinclude subforms. When an application designer creates mobile versionsof existing forms in a wireless access application, the alias for themobile forms may be the existing form name or the existing form aliasname. For example, an email application may have a mobile form namedMobileMemo, which may be a modified version of the Memo form. The aliasfor the MobileMemo form may be “Memo”. This allows documents created ona mobile device and saved on the server to be viewed properly from theclient or a web browser. It also allows form names saved in documents tobe matched with the names of mobile forms.

[0068] An application designer may also create multiple forms with thesame alias. This may be useful for allowing the end user to choose theform to use to display or edit documents. The application designer mayalso designate that a form be used only for reading or only for editingdocuments. Other restrictions may also be applied. Default forms may bespecified as well.

[0069] Form may support varying components, such as text, field,subform, default actions (e.g., categorize, send document, forward, moveto folder, remove from folder), custom actions, images, and otheractions.

[0070] Form properties used in a wireless access application form mayinclude name, which may be used as a form name when selecting a form todisplay a document on a mobile device; alias, which may be used as aform name in a document when creating a new document on a mobile device;type, which may be used when creating a response document on a mobiledevice; automatically enable edit mode; and default read access fordocuments created with the form, which may be used to determine whetherthe user is allowed to use the form on the mobile device. Other formproperties may also be available.

[0071] Varying fields may be supported in a form or subform, such asrich text, text, date/time, number, checkbox, radio button, listbox,authors, names, readers and other fields. Rich text fields may betreated as simple text fields when sent to a mobile device where thetext may be used and any embedded objects may be ignored or otherwisesuppressed. However, attachments and other objects may be addressed. Forexample, when an attachment appears in a rich text field, a textreplacement string may be substituted for the attachment in the textstream sent to the mobile device. Rich text fields in a wireless accessapplication may also be assigned a truncation property, where apredetermined number of bytes of field (or number of characters)contents may be sent to the mobile device.

[0072] Text fields may allow for multiple values, for example. Textfields in a wireless access application may also be assigned atruncation property in a similar manner as Rich text fields. Text fieldsmay also be assigned a “Mail To” property. If a form has a text fieldwith a “Mail To” property, then whenever a document is displayed withthis form a “Mail” action may be available on the mobile device. Themail action may allow the user to create an email (or other message)with the “To” field pre-filled with the value of this field. If morethan one field in a form has the “Mail To” property, then the user maybe presented with the available email address choices.

[0073] Text fields in a wireless access application may also be assigneda “Dial Phone” property. If a form has a text field with a “Dial Phone”property, then whenever a document is displayed with this form, a “Call”action may be available on the mobile device. The “Call” action mayallow the user to dial the phone number contained in this field. If morethan one field in a form has the “Dial Phone” property, then the mobiledevice user may be presented with the available phone number (or othercontact information) choices.

[0074] Date/Time fields format may be determined from the mobile user'slocale settings. Local time zone may also be determined from the mobileuser's locale settings and the time may be displayed on the device aslocal time.

[0075] Number fields may support field properties, such as number format(e.g., decimal, percent, currency); decimal places; decimal symbol;thousands separator; currency symbol and other field properties.

[0076] Multiple types of forms may be used by the present invention forvarious applications. Different types of forms may include facsimile,memorandum, invitation, user profile and other applications. Forms foreach application may include predetermined form fields that are specificto each application. Forms may be created, modified and forwarded (orsent) to one or more selected recipients. Other operations may also beperformed.

[0077] For example, forms may be displayed as brief forms and fullforms. Other options are also available. For example a full form maydisplay all the fields available while a brief form may display thefields selected (or customized) by the user.

[0078] For example, a brief memo view may display a selected portion ofa memo, such as the body of the text. If the body field is longer thanthe screen size, then a portion of the body field may be displayed.Other fields may be selected by the user. A full memo view may include afrom field, date field, send to field, copy to field, subject field,body field and other fields. Actions associated with a memo may includereply, delete, fax, forward, switch view and other actions and viewingoptions.

[0079] For example, a brief invitation view may display one or moreselected fields or portions of an invitation, such as start date field,end date field, and subject field, for example. Other fields or portionsof the invitation may be selected. A full invitation view may includechair field, start date field, end date field, location field, subjectfield, comments field, body field and other fields. Actions associatedwith an invitation may include accept, decline, fax, switch view, andother actions and viewing options.

[0080] A fax form may include a name prompt; fax number, comment andother fields. A fax menu may include send, cancel, save as draft andother operations. The fax may be sent to one or more recipients selectedfrom an address book, directory or other database.

[0081] Privacy features may also be available in wireless accessapplications of the present invention. For example, a “Prevent Copying”option may be used when composing an email message or other document orcorrespondence. A message (or document) designated with the “PreventCopying” option may not be forwarded or faxed. Various privacy optionsand levels of privacy may be available. For example, if a user selectsmultiple messages to forward or fax, those messages designated asprivate may be ignored (e.g., those messages may not be forwarded orfaxed). If all selected messages are designated as private, than anerror message may be displayed to the user. If a user elects to replywith history to a message designated as private, then the reply may besent without the contents of the original message. An error message mayor may not be given. If a message has a different level of privacyattached to it, then forwarding and reply with history may worknormally, but faxing may be prevented. Other levels and forms of privacymay be designated for different messages, documents and applications.

[0082] An application designer may create views and folders, throughView/Folders module 416, that the end user may use to list documents andother correspondences, for example. Each wireless access application maycontain at least one view or folder. A view may contain one or morevarious components and properties, such as name, view selection formula,default actions, columns and other actions. According to an embodimentof the present invention, application navigation may occur through viewsand folders where the user may open a selected document from a list ofviews and folders.

[0083] Columns may support properties, such as column value, title, sortorder, click on header to sort, multi-value separator, number formats(e.g., general, fixed, currency, percentage, etc.), decimal places, dateand time content (e.g., date and time, date only, time only) and otherproperties. Formatting information for number column values may bedetermined from a mobile user's local settings, such as decimal symbol,thousands separator, currency symbol and other formatting information.The format for date/time column values may be determined from a mobileuser's locale settings. Locale time zone may also be determined from themobile user's locale settings and time may be displayed on the device aslocal time. Column contents may be designed so that a maximum of apredetermined number of characters may be display for any column. Ifnecessary, field values used as column content may be truncated.

[0084] An application designer may include a Using Database Documentwith a wireless access application. This may cause an action menu itemto be included with each view/folder that may be used to read the UsingDatabase Document. The components allowed in a Using Database Documentmay be text and BMP images. Other components may also be available.

[0085] A wireless access application may contain default, custom andother actions, which may be accessed through Default and Custom Actionsmodule 418. Default actions may be supported in one or more of forms,views and folders. Custom actions may be supported in forms andsubforms. Custom actions may be written using a particular language,such as WML script or other language. For an action to be included inmobile wireless access application, the display property “Include actionin Action menu” or similar display property may be selected for theaction.

[0086] Default actions may support various actions, such as categorize,send document, forward, move to folder, remove from folder and otheractions. Categorize action may add one or more categories to thecategories field of a document. Send document action may add one or morerecipient names to a send to field of a document. Forward action may addone or more recipient names to a send to field of a memo form and add adocument to the body field. Move to folder action may add a document toa folder. Remove from folder action may remove a document from a folder.

[0087] A wireless access application may contain script in certaincontexts, according to an embodiment of the present invention. Variouscomponents may be available for scripting, such as form events; customactions; field defaults, input translation and input validation;computed fields; column values and other components. A subset of@function language (“FL”) may be supported as well as WML Scripts(“WMLS”). Other scripts may also be supported. WML Script may besupported for certain events. In order to access field values, a WMLbrowser and functions may be used. Because the WML syntax for variablenames may differ from the syntax for field names, name mapping may beperformed according to various predetermined rules.

[0088] According to another embodiment of the present invention, awireless page generator may format the document, view, page (or otherinformation) into an appropriate format for the device. A wireless pagegenerator of the present invention may receive requests for and generatepages of data to be sent to and displayed on a wireless device. A pagegenerator may also encompass a XML to WML translator. For example, thedata may be in WML for display on a WAP phone or other mobile device. Inanother example, it may be data intended for an iMode, HDML or otherdevice. Other applications may be implemented.

[0089] Requests for a page of data may come from one or more requesthandlers. A page of information requested for display on the device maybe of several different types. For example, information requested fordisplay may include a document from a database formatted by a form. Tocreate this type of page, the page generator may take the appropriatedata from the database and transform the data based on a style sheetspecific to the type of device it is to be displayed on.

[0090] Also, information requested for display may include a list ofdocuments in a database, selected and formatted by a view or folder.This process may be similar for documents and forms. A list of entriesin the view may be obtained from a database, the details of thoseentries may be read, and the data may then be transformed by a stylesheet into the requested (or desired) format.

[0091] The page of information requested may also encompass a fixed (orpre-determined) pregenerated page of data, such as a database containinga “Using” or “Help” document. The page of information may also includefiles to be sent to the phone (or other device), for example, a scriptfile required (or requested) by the page on the phone. These may bescripts defined in a form, but in WML they may be sent separately to thephone (or other mobile device). Another example may include an imagefile.

[0092] The page of information requested may also include a user's homepage, listing mobile applications a user may be authorized to access andother information. The options available on the user's home page, andthe associated URL to open may be stored in a document in anadministration or other database. This may be merged with an appropriateHome Page style sheet to create a page specific to the device.

[0093] The page of information requested may also include a mobileapplications main menu. For example, an email application may offer“read new mail”, “create email”, etc. Another example may include errormessages, such as “error opening database” or “authorization to opendatabase denied”. The error message text may be generated from anappropriate resource file.

[0094] This text may then be transformed by a style sheet into theformat required (or requested) by a device (e.g., WML).

[0095] A database designer (or other authorized entity) may define oneor more mobile applications in a database. According to an embodiment ofthe present invention, each mobile application may create an “AppDigest” in a database. An App Digest may be a form. Examples of formsmay include “email” or “calendar”. One function of the App Digest may beto hold information regarding the application and a copy of the designelements used by the mobile application in a format required (ordesired) by the mobile service.

[0096] Mobile design elements (e.g., document and view style sheets,pre-generated pages and scripts) may be saved in the App Digest asattached files. These mobile design elements may be intended to bederived from equivalent design elements in a database (e.g., forms,views, help, etc.). A compiler may automatically generate these itemsfrom forms and views designed by an application designer. Also, stylesheets and pages may be hand coded.

[0097] A wireless App Digest may contain various attachments with namesin a format which may include device type and device model. Files may bein a structured field format containing various design elements (e.g.,style sheets, pre-formatted pages, etc.) and associated information (forexample, each style sheets may need an associated form name, such as“memo”). If a design element is not found in the appropriate devicetype/device model file, then the page generator may look in a genericdevice type file. In this way, if there are significant differencesbetween devices of the same type, the relevant style sheet may beincluded in each of the files whereas if each model behaves the same (orsimilarly), a single style sheet may be put in a generic device typefile.

[0098] If a request handler requests a pre-generated page or a script,the appropriate page of data may be read from the App Digest andreturned to the request handler. If a request handler requests adocument, a view or any other page that may be formatted by a stylesheet, the page generator may obtain and merge information from thesources. Thus, the values of the fields in the document may be read andformatted on a screen according to the layout specified in the form. Thewireless page generator may format the document, view, page (or otherinformation) into an appropriate format for the device.

[0099]FIG. 10 illustrates a process for formatting a document (or otherpage of data) in an appropriate format for a device, according to anembodiment of the present invention. At step 1010, the document may bepre-processed to replace one or more elements that may not be able to bedisplayed or otherwise hindered (e.g., encrypted fields or fileattachments), which may include text indicating what has been removed(or altered). Also, data types that may not be able to be represented ona device (e.g., date/time fields) may be converted into text. Forexample, date/time fields may be replaced with text giving the date inthe user's local time zone, which may be formatted according todate/time zone preferences. In another example, fields may be truncatedthat have been marked in the design as being truncatable, to a maximummobile size. Fields that have not been marked as truncatable may betested for size based on the maximum size of WML the device may accept.Also, the size the style sheet can be without this data may also beconsidered.

[0100] At step 1012, a mobile XML description may be obtained of adocument data or view. At step 1014, an XSL style sheet may be read froman App Digest. At step 1016, the appropriate style sheet may be compiled(or generated). At step 1018, the XML document may be transformedaccording to the style sheet using an XSLT processor and return theresulting page of data to a request handler or other authorized entityor unit.

[0101] For further improvement, the design elements of an applicationmay be cached by the page generator, since these items may not changefrequently. In the case of style sheets, the compiled style sheet may becached. In addition to the design elements required (or desired) for aparticular application, there may also be a number of common designelements required (or desired) by the mobile service. These may bestored in a mobile application form in an administrative (or other)database. Design elements included in this application may include astyle sheet to build an error message to send to a device and a stylesheet to build a home page. Other design elements may also be designatedas such.

[0102] Multiple mobile device types may be supported through the presentinvention. According to an embodiment of the present invention, ageneric output may be provided where the specifics related to thereceiving mobile device may be irrelevant. For example, regardless ofthe model, type or series number of the mobile device being used,information sent to the mobile device may be viewed properly. Furtherthe information may be customizable by the user.

[0103] Mobile device users may customize various aspects of views andapplications, through Customization module 420. Examples of customizableoptions may include home page (e.g., personal, any URL), time zone, dateformat, font format, language and other options. This feature of theinvention provides for international applications. For example, a usermay receive a message in French from a client in France or otherlocation. The text message in French may be accepted by a mobile deviceand displayed in French or English (or other selected language). Thedata transmitted may be formatted to display an identified time zone,date format and other features and characteristics for customizedviewing options.

[0104] A server form in a directory of the present invention may containa subform that allows server level configuration information to beadministered. The subform may contain various tabs, such as Basics tab,Wireless Access tab and Wireless Security tab. Basics tab may containserver settings which may be common to various applications andproducts. The Wireless Access tab and the Wireless Security tab maycontain server settings specific to a wireless product.

[0105] Server locale information may be used when sending date, time andcurrency information to a wireless device. However, the time zoneinformation, the date format and other information may be over-ridden bya user via the wireless user settings in an appropriate form, e.g.,Person form.

[0106] The Person form in a directory may contain a subform that allowswireless user settings to be administered. Wireless user settings may beoptional. For example, wireless user settings related to time may beadministered by a user from a wireless device.

[0107] According to another embodiment of the present invention, awireless servlet may use an attachment to a user's Person document todefine and save application specific preferences, such as mobile formpreferences, search key values and other preferences. This attachmentmay be similar to a web “cookie” and may contain information that maynot be directly administered at the server. For example, a user maysubmit a search or series of searches in an application (e.g., email orcalendar). The user may enter search criteria, which may include searchterms, strings of characters and other information in a search form.This search criteria may be saved in a file, as an attachment, forexample. Also, the search criteria may be stored on a client sidedevice, such as the mobile device. When a subsequent search isconducted, the previous searches may be accessed and/or retrieved. Thisfeature of the present invention may facilitate searching techniques bythe user.

[0108] A wireless user home page form may be used to configure aninitial menu for a user when accessing a wireless servlet. A defaulthome page document may also be available. Each user home page entry mayinclude various types. For example, a wireless request may be sent to acurrent wireless server, a URL to any web page, or a submenu for morehome page entries. Other options may be available. If a user's home pagehas a single request or URL menu item, then that item may be executed.

[0109] An application designer may design an application user profileform. The application user profile form may enable the user to choosethe form to be used when viewing or editing documents (or otherinformation) on a mobile device. Also, application user profile form mayenable the user to choose a default view to be used when viewingdocuments (or other information) on the mobile device. Application userprofile form may also enable the user to manage and choose words orphrases for fields in a form.

[0110] The user may select the form to be used on a mobile device whenreading or editing documents. The user may select a mobile form for eachapplication form that is used. For example, if an application has aSales form, the application designer may create two mobile versions ofthis form called MobileSales and BriefSales, both with alias Sales. Theuser may choose either MobileSales or BriefSales as the form to use forreading Sales documents on the mobile device. If the application hasanother form, then the application designer may create multiple mobileversions of that form and the user may also choose which to use forreading or editing documents of that type. Other options and variationsmay also be implemented.

[0111] The user may select a default view to be used on the mobiledevice when reading documents and performing other operations.

[0112] If the application designer adds text fields to the user profileform with the same (or similar) field names as fields in the wirelessaccess application form, then the user may add a list of names, words orphrases which may then be selected on the mobile device as values forcorresponding fields. This may be similar to a keyword field type in aform. Further, the user may modify the list. For example, for an emailapplication, the user profile form may contain a text field with thename Subject. The user may then add phrases such as “Sales Status”,“Just saying hello”, “Can we meet?” to this field and those phrases maybecome choices for the content of the Subject field in a Memo (or other)form when sending an email (or other document) from a mobile device.

[0113] An application designer may design an application search form. Ifan application has a search form, then users may have the option tosearch (as well as open and perform other operations to) the applicationfrom their home page or other environment. If a user chooses to searchan application, then the search form may be opened for editing on amobile device where the user may submit various search settings. Thesearch form may be a profile form and each user may have a profiledocument containing the last or previous search settings used, as wellas other information.

[0114] A search form may contain a formula field where the field maycontain a select formula that may be evaluated on the server for thesearch operation. This formula typically may reference other fields onthe search form. For example, a designer may add a From field on anemail application search form so that the user may search for email froma particular person or group. Also, a search form may optionally containa field that may contain a view or folder name which may be used tofurther constrain the search to documents in a specified view or folder.Other specifications may be defined and other criteria may be applied.

[0115] According to another embodiment of the present invention,text-to-speech capability may be provided. Thus, any information in theform of text received by a mobile device may be converted to speech.

[0116] The features of the present invention may be applied to afinancial services example. However, it may be understood that thepresent invention may be applied to various applications. This followingexample of financial services is presented as a mere example of thepresent invention. A financial planner (or user) or other entity doingbusiness in the financial field may have various stocks to manage. Thefinancial planner of this example may have set buy and sell thresholdsfor each stock. Timing is critical and a delayed buy or sell may mean adifference of hundreds of thousands to various clients. However, thefinancial planner may not be able to constantly monitor the market.Through the present invention, any time the price reaches an upper orlower threshold, the present invention may notify mobile services andusing a short messaging or other services a short message may be sent tothe financial planner where a mobile device (e.g., pager, cell phone)may alert the financial planner. However, the financial planner may bein a situation where immediate action may not be possible. For example,the financial planner may be in a meeting, in an airplane or otherwiseunable to react to the message. Through the present invention, thefinancial planner may have programmed the mobile device (e.g., pager) sothat with a single press of a button, the financial planner may direct amessage to a broker (or other entity). If the financial planner isnotified that one of the stocks has reached the critical point, thefinancial planner may simply pick a reply (e.g., sell, buy, hold) andforward the message to the broker (or other selected recipient) withouthaving to leave a meeting or make a call.

[0117] The method and system of the present invention may be implementedthrough various communication environments, such as a WirelessApplication Protocol, Bluetooth protocol, Global System Mobile protocol,Wireless Markup Language protocol and other wireless communicationprotocols. Bluetooth wireless communications technology provides theability to exchange data and voice between communication devices.Bluetooth may include a radiobased standard for small personal devicesto automatically connect and exchange information for personal wirelessapplications. Bluetooth may further include a short-range networkingprotocol for connecting different types of devices, such as mobilephone, desktop or notebook computers. Bluetooth may enable access to theInternet via a phone's mobile data system and linking the user's voiceto a computer. Devices that are Bluetooth enabled may communicate bywireless signals within a defined range where a line-of-sight connectionis not needed. For example, Bluetooth technology may transfer an emailfrom a user's cell phone to a PC for easier reading and reply.

[0118] Bluetooth may enable the creation and use of wireless personalarea networks (“WPANs”) where a WPAN may connect devices to establishdata communications channels for applications. The WPAN may form anetwork for a single individual and that person's interactions withpersonal digital devices. Bluetooth may be a packet-based communicationsmedium and may accommodate both data and voice transmissions.

[0119] The foregoing description of a system and method for providingcustomizable options on a wireless device is illustrative, and changesin the above construction and sequences of operation may occur topersons skilled in the art. For example, although multiple modules areshown for carrying out the invention, additional or fewer modules may beused and multiple modules may be positioned in various locations. Otherembodiments, uses and advantages of the present invention will beapparent to those skilled in the art from consideration of thespecification and practice of the invention disclosed herein. Thespecification and examples should be considered exemplary only. Thescope of the invention is accordingly intended to be limited only by thefollowing claims.

What is claimed is:
 1. A method of customizing the presentation ofnetworkable media, comprising the steps of: (a) selecting at least onepresentation option for transmissable media content; (b) receiving thetransmissable media content via a wireless medium; and (c) presentingthe transmissable media content to a user according to the at least onepresentation option.
 2. The method of claim 1, wherein the selecting ofstep (a) comprises a step d) of selecting at least one of a home page, atime zone, a date format, a font format, and a language.
 3. The methodof claim 1, wherein the step (b) of receiving comprises a step of e)communicating via at least one of a Bluetooth protocol, a WirelessApplication Protocol, a Global System Mobile protocol and a WirelessMarkup Language protocol.
 4. The method of claim 1, wherein the step c)of presenting comprises a step of f) presenting the transmissable mediacontent via a display screen of a wireless client device.
 5. The methodof claim 4, further comprising a step of g) storing the at least onepresentation option in the wireless client device.
 6. A system forcustomizing the presentation of networkable media, comprising: an inputinterface to accept at least one presentation option for transmissablemedia content; a communications interface for receiving thetransmissable media content via a wireless medium; and a processor unit,connected to the input interface and the communications interface, theprocessor unit configured to present the transmissable media content toa user according to the at least one presentation option.
 7. The systemof claim 6, wherein the processor unit presents at least one of a homepage, a time zone, a date format, a font format, and a language.
 8. Thesystem of claim 6, wherein the receiving of the transmissable mediacontent comprises communicating via at least one of a Bluetoothprotocol, a Wireless Application Protocol, a Global System Mobileprotocol and a Wireless Markup Language protocol.
 9. The system of claim6, wherein the presentation comprises presenting the transmissable mediacontent via a display screen of a wireless client device.
 10. The systemof claim 9, wherein the processor unit stores the at least onepresentation option in the wireless client device.
 11. A system forcustomizing the presentation of networkable media, comprising: inputinterface means to accept at least one presentation option fortransmissable media content; communication interface means for receivingthe transmissable media content via a wireless medium; and processormeans, communicating with the input interface means and thecommunication interface means, the processor means configured to presentthe transmissable media content to a user according to the at least onepresentation option.
 12. The system of claim 11, wherein the processormeans presents at least one of a home page, a time zone, a date format,a font format, and a language.
 13. The system of claim 11, wherein thereceiving of the transmissable media content comprises communicating viaat least one of a Bluetooth protocol, a Wireless Application Protocol, aGlobal System Mobile protocol and a Wireless Markup Language protocol.14. The system of claim 11, wherein the presentation comprisespresenting the transmissable media content via a display screen of awireless client device.
 15. The system of claim 14, wherein theprocessor means stores the at least one presentation option in thewireless client device.
 16. A storage medium for storing machinereadable code, the machine readable code being executable to customizethe presentation of networkable media according to the steps of: (a)selecting at least one presentation option for transmissable mediacontent; (b) receiving the transmissable media content via a wirelessmedium; and (c) presenting the transmissable media content to a useraccording to the at least one presentation option.
 17. The storagemedium of claim 16, wherein the comparing of step (b) comprises a stepof d) of selecting at least one of a home page, a time zone, a dateformat, a font format, and a language.
 18. The storage medium of claim16, wherein the step (b) of receiving comprises a step of e)communicating via at least one of a Bluetooth protocol, a WirelessApplication Protocol, a Global System Mobile protocol and a WirelessMarkup Language protocol.
 19. The storage medium of claim 16, whereinthe step c) of presenting comprises a step of f) presenting thetransmissable media content via a display screen of a wireless clientdevice.
 20. The storage medium of claim 19, further comprising a step ofg) storing the at least one presentation option in the wireless clientdevice.